Magnum One

home *** CD-ROM | disk | FTP | other *** search

/ Magnum One / Magnum One (Mid-American Digital) (Disc Manufacturing).iso / d1 / co_sessn.arc / READ-ME < prev next >

Wrap

Text File | 1988-05-23 | 30KB | 659 lines

"READ-ME" FILE - CO/SESSION VERSION 3.0 March 29, 1988 Welcome to version 3.0 of CO/SESSION. This file supplements the current User's Guide with the new features, enhancements, and corrections which have occurred since our last document release. The following topics are discussed below: o DEMONSTRATION VERSION RESTRICTIONS o USER REGISTRATION CARDS o COMPATIBILITY WITH EARLIER CO/SESSION VERSIONS o INSTALLING CO/SESSION FROM A: OR B: DRIVE o INSTALLING CO/SESSION ON A SINGLE DRIVE SYSTEM o NOVELL NETWORKS o ALLOY PC-PLUS SLAVE CARDS o SUPPORT KEYBOARD COMMANDS o ENHANCED SECURITY -Dial-Back -File Transfer Access Rights -Directory Access Restriction o FILE TRANSFER OVERWRITE VERIFICATION o DATA COMPRESSION AND FILE TRANSFERS o BACKGROUND COMMUNICATIONS o VOICE FIRST o COM PORT WINDOW o DIRECT CABLE CONNECTIONS o ADDITIONAL MODEM SUPPORT o COM3 and COM4 SUPPORT o TTY TERMINAL EMULATION o CONFIGURATION SETTINGS o ANSI.SYS and SIMILAR DEVICE DRIVERS o REMOTE PRINTING o MAKING APPLICATION PRINT MODE PERMANENT o UNATTENDED REMOTE ACCESS o THE DEFAULT CALL ID RECORD o QUICK CONNECTIONS TO A PRIMARY SITE DEMONSTRATION VERSION RESTRICTIONS Your CO/SESSION(tm) demonstration version is the full CO/SESSION version, and all features and functions of the full version are available. However, there are several constraints on the demonstration version which distinguish it from the full CO/SESSION version. The constraints on the CO/SESSION demonstration version are: (1) the maximum total connect time allowed is approximately 15 minutes; you can use the 15 minutes on one connection or on several connections less than 15 minutes; once the total 15 minutes of allowable connect time is used; no subsequent connections are permitted; if you are currently connected, you are warned of the approaching 15 minute limit and when reached, the connection is terminated; you must reboot and reload the CO/SESSION demonstration version to get another 15 minutes of connect time; (2) the maximum number of Call IDs permitted is 2; (3) the maximum file size permitted to be uploaded or downloaded from a remote CO/SESSION machine is 5000 bytes; after 5000 bytes the file transfer is terminated; (4) password sending/checking is not supported, so the security features such as Dial-Back and File Transfer Access rights are not functional; (5) remote printing is inhibited. USER REGISTRATION CARDS Please fill out your User Registration Card in the back of the User Guide so that we may inform you of upcoming new releases and products. COMPATIBILITY WITH EARLIER CO/SESSION VERSIONS Version 3.0 incorporates enhanced screen data compression techniques which result in a faster Support PC screen update versus earlier CO/SESSION versions. An older Application IS compatible with a 3.0 Support. However, a 3.0 Application is NOT compatible with an older Support. INSTALLING CO/SESSION FROM AN A: OR B: DRIVE INSTALL has been updated so that you may install CO/SESSION from floppy drive A: or B:. You may type "A:INSTALL" or "B:INSTALL" depending on which floppy drive has the CO/SESSION master diskette. INSTALLING CO/SESSION ON A SINGLE DRIVE SYSTEM Follow the instructions below for installing CO/SESSION on a PC with only a single disk drive. 1) Create a copy of the original diskette and store the original in a safe place. 2) Create the file "session.bat" on the newly created CO/SESSION diskette. The file will include the following information for either loading the support or application versions of CO/SESSION. SESSION.BAT - Support Version echo off a:support -ea:\ -da: -p\ SESSION.BAT - Application Version echo off a:applica -ea:\ -da: -p\ To invoke CO/SESSION, place the newly created CO/SESSION diskette in the drive and type "session". CO/SESSION will be loaded into memory and available for use. NOVELL NETWORKS When using CO/SESSION on a Novell network rename the file "session.bat" to prevent any conflicts with Novell's "session" command. "Session.bat" is created during the CO/SESSION installation process and specifies proper disk, directory and path information for loading CO/SESSION. ALLOY PC-PLUS SLAVE CARDS CO/SESSION works with ALLOY's PC-PLUS network slave card and NTNX software product, but with some limitations. CO/SESSION must be loaded into one of the slave card "partitions" rather than at the "main console", and an external modem only can be supported by plugging into COM2, the DB-25 pin port of the slave card. The cable between the modem and the COM2 port should have pin-22 disabled to prevent a reboot of the slave card when the modem answers a dial-in. COM1 on the slave card is a DB-9 pin port and is used for connecting a terminal. CO/SESSION can be automatically loaded by placing the command to load CO/SESSION ("SESSION") into the AUTOEXEC file associated with the slave card, for example, "AUTOEXE.U01". CO/SESSION can be loaded from the "main console" into a slave card by using the NTNX command program, "C". You activate this by pressing <Alt><F10>. After pressing <Alt><F10>, type <C>, then respond with the user number for the slave card, then type the CO/SESSION load command, "SESSION". SUPPORT KEYBOARD COMMANDS From the SUPPORT PC, either <Ctrl><Alt> or <Ctrl><LeftShift> in conjunction with: <R> - causes SUPPORT PC screen redraw; <F> - causes APPLICATION PC to run in "full-speed" mode; <S> - causes APPLICATION PC to run in "synchronized" mode; <T> - causes APPLICATION PC to run in a "fast-graphics" mode, which if in a CGA graphics mode results in every other line of screen graphic data to update the SUPPORT PC; <M> - causes APPLICATION PC to process the display screen according to the Video Mode Synchronize parameter in the configuration settings; this is useful when using programs that change the video mode without following the "normal" rules so that CO/SESSION cannot automatically detect the video mode change. ENHANCED SECURITY Several new security features have been added so that you may customize and provide the level of security you require. (1) Dial-Back There is now a "Dial-Back" feature that you may set on an individual Call ID basis. It will disconnect and call back a remote user at a predefined telephone number when that remote user attempts to connect to your computer. To use the "dial-back" feature, you must have the Password Protection Checking option <M>, in the configuration settings, set to YES; next, in the Call ID parameter record where you have defined the expected Login and Password for the remote user, set the "Dial-Back" field option to YES; and then define the remote CO/SESSION user's telephone number in the telephone number field of the Call ID parameter record. (2) File Transfer Access Rights There is now a feature that permits you to define on an individual Call ID basis, what file transfer access rights you want the remote CO/SESSION user to have in accessing your computer. You may define ALL transfer rights allowed, NONE allowed, SEND ONLY to your computer, or RECV ONLY from your computer. The file transfer rights are defined from the perspective of the remote CO/SESSION user. To use the "file transfer access rights" feature, you must have the Password Protection Checking option <M>, in the configuration settings, set to YES; next, in the Call ID parameter record where you have defined the expected Login and Password for the remote user, set the "File Transfer Rights" field option to ALL, NONE, SEND ONLY, or RECV ONLY. (3) Directory Access Restriction There is now a feature that allows you to restrict the access of the remote CO/SESSION user to particular drives and directories on your computer. This feature is further described below as the <U> option in the Configuration Settings. FILE TRANSFER OVERWRITE VERIFICATION On all CO/SESSION file transfers, if the destination file already exists, you are prompted to verify before the transfer is started that it is OK to overwrite the destination file. DATA COMPRESSION AND FILE TRANSFERS CO/SESSION's file transfer protocol automatically utilizes a very efficient data compression algorithm to increase the file transfer rate, saving time and money. There is no need to use additional utilities such as "arc" or "squeeze" to compress your files before using CO/SESSION's file transfer. BACKGROUND COMMUNICATIONS A CO/SESSION support user can transfer, display or delete files on an application user's PC "in the background" while the application user is running a program "in the foreground". Once connected, the support user can display the CO/SESSION File Functions Submenu and initiate file transfers or other functions while the application user continues running his current program. VOICE FIRST This feature lets you make a voice telephone connection with the remote user, or to a switchboard operator, and then at any time after, switch to a CO/SESSION data connection without having to hang-up and redial. This requires that the modems each of you are using are connected to the same line as your telephone. Most modems have a separate jack in the back where you can plug in your telephone. For those that do not, you can use a y-connector to plug both your telephone and modem to the same wall jack. With this feature, it is not even necessary to have CO/SESSION loaded when you first make the voice connection. You can also use this feature to call through a switchboard to reach a remote PC that is unattended. As long as the remote unattended PC has CO/SESSION loaded and is in auto-answer mode, or you are using a power-on device with it (see UNATTENDED REMOTE ACCESS below), after the switchboard operator connects you through to the unattended location, follow the same steps described below. When you and your remote user are both ready to switch to a CO/SESSION data connection, do the following: (1). If CO/SESSION is not already loaded, do so now. (2). Bring up the CO/SESSION Main Menu on both computers. (3). Press the <F7> function key (Voice/Data Toggle). If you are currently the SUPPORT type, you are prompted as to whether you are going to remain as the SUPPORT type. You respond with 'Y' or 'N', for yes or no. One of you must be an APPLICATION type, and the other must be the SUPPORT type. If you respond 'Y' to the prompt, CO/SESSION assumes the other user is the APPLICATION. (4). Next, listen in your telephone handset for the modem tones. If the connection between the modems is successful, CO/SESSION tells each of you with a notification message, and then automatically starts the login procedure. If all is successful, the SUPPORT user's PC screen is updated with the APPLICATION user's PC screen data. At this point, hang-up the telephone handsets. (5). If the modems do not successfully connect, you should still have your voice connection. Try it again until you successfully get the modems to connect. You must have the port parameters of the Call ID DEFAULT set to the port, baud-rate, modem type, and terminal type that you are using so CO/SESSION knows what to use when you press <F7>. See THE DEFAULT CALL ID RECORD section below. COM PORT WINDOW This feature is available as <F4> on the Communications Menu and provides a pop-up window where you may type any commands or data that you require directly to the communication port. The COM port and baud-rate used is that which is defined in the Port Parameters of the Call ID selected when you press <F4>. This feature, available when you are not yet connected, is useful for providing communication directly to the attached modem or PBX device. Thus, with this feature, you may use any non-Hayes compatible modem with CO/SESSION, or you may command your PBX to connect you to the modem pool. When you select this function, the Data Terminal Ready (DTR) signal is raised high by CO/SESSION, and when you exit the COM Port Window, DTR is left high. To reset, you can press <F6> Disconnect/Hangup. When you exit the COM Port Window, you may then use the <F1> Call or <F2> Wait For Call functions to make a CO/SESSION connection. If you have used the COM Port Window to dial a non-Hayes modem and connect to the remote modem, use <F1> Call function with the modem type in the Call ID you have selected set to "Direct Cable" to start the automatic CO/SESSION login connection sequence. If you have used the COM Port Window to connect to your modem pool through your PBX, use <F1> Call function with the modem type in the Call ID you have selected set to the Hayes or compatible modem you are using and let CO/SESSION dial for you. DIRECT CABLE CONNECTIONS The minimum direct cable wiring requirement is now pins 2 & 3 reversed, that is, pin 2 on one end goes to pin 3 on the other end, and pin 3 goes to pin 2; however, if you also reverse pins 6 and 20, disconnects from the other computer are detected by CO/SESSION. ADDITIONAL MODEM SUPPORT Additional modem types have been added, and the complete modem list now appears in a pop-up window when you are at the Call ID parameter screen and you select the Modem Type parameter option by pressing the <M> key. For the MICROCOM-AX series of modems, set the front switches 2 and 8 down, and set the rear switches 6 and 7 down, all other switches up. COM3 and COM4 SUPPORT Support for communication ports COM3 and COM4 has been added; COM3 is defined as using IRQ4 and port address 3E8; COM4 is defined as using IRQ3 and port address 2E8. It is possible to patch the appropriate CO/SESSION tables if you want to use a different IRQ and/or port address. The procedure is as follows: (1) Copy the SUPPORT.EXE or APPLICA.EXE to another file with the name SUPP or APPL, without the ".EXE" extension. (2) Use DEBUG.COM that comes with DOS to load and patch the file, type the following: debug supp<Enter> or debug appl<Enter> (3) At the DEBUG prompt, which is a minus sign ( "-" ), locate the appropriate tables; first, determine the value of the CS register using the "R" command; second, add 1000 hex to the value of CS to determine the segment; then, display the tables with the appropriate offset using DEBUG's display memory command; the offset for SUPP is E0E0 hex; the offset for APPL is 3C80 hex; for example, type the following: R<Enter> ;display registers, assume CS=2A42 D 3A42:E0E0<Enter> ;CS+1000 and offset for SUPP The data displayed is defined as follows: offset+0 = COM1 interrupt vector number = 0C offset+1 = COM1 mask for the IMR = 10 offset+2 = COM2 interrupt vector number = 0B offset+3 = COM2 mask for the IMR = 08 offset+4 = COM3 interrupt vector number = 0C offset+5 = COM3 mask for the IMR = 10 offset+6 = COM4 interrupt vector number = 0B offset+7 = COM4 mask for the IMR = 08 offset+8 = COM1 port address = F8 03 offset+A = COM2 port address = F8 02 offset+C = COM3 port address = E8 03 offset+E = COM4 port address = E8 02 (4) Based on the IRQ you want to use, get the proper values from below, then patch the table for the port that you want to redefine; the values are as follows: IRQ 5 - interrupt vector number = 0D - mask for the IMR = 20 IRQ 4 - interrupt vector number = 0C - mask for the IMR = 10 IRQ 3 - interrupt vector number = 0B - mask for the IMR = 08 IRQ 2 - interrupt vector number = 0A - mask for the IMR = 04 (5) Patch the tables using the DEBUG "E" command; for example, if you want to set up COM3 to use IRQ2 and port address 3C8 in the SUPP version, and CS=2A42, you would type the following; E 3A42:E0E4<Enter> ;DEBUG will display the value at the location and allow you to change it; type the new value followed by space to get the next location; 0A<SpaceBar> ;default value should be 0C 04<Enter> ;default value should be 10 E 3A42:E0EC<Enter> ;change the port address for COM3 C8<SpaceBar> ;default value should be E8 03<Enter> ;default value should already be 03 (6) Finally, write the changes back to disk using the DEBUG "W" command and quit DEBUG; type the following: W<Enter> Q<Enter> Then, copy the patched SUPP or APPL version back to the SUPPORT.EXE or APPLICA.EXE version. TTY TERMINAL EMULATION The TTY terminal emulation function has been enhanced so that pressing the <F9> function key while at the TTY emulation screen will cause a 330 millisecond BREAK to be sent. Also, pressing the <Esc> key is now passed on. Pressing the <Ctrl><Alt> will pause from receiving and displaying terminal data so that you may select any of the TTY functions. After a function selection, receiving and displaying terminal data will resume. The <F4> function key on the CO/SESSION Main Menu is used only to return to the TTY emulation screen after you have already made a TTY emulation connection. Refer to page 37 in the User's Guide for more information on the TTY terminal emulation. CONFIGURATION SETTINGS Page 94 of your User's Guide describes in detail the available CO/SESSION configuration settings. By becoming familiar with these options you will be able to maximize your use and productivity with CO/SESSION. Four new Configuration Setting options have been added: <R> On-line HELP Handler - defaults to YES which means CO/SESSION Help is available by pressing <Ctrl><?> when in the menus; NO suppresses the HELP handler and avoids the need to "take-over the keyboard interrupt vector; this may be useful if a conflict occurs, when in CO/SESSION menus, with a keyboard utility; <S> Screen-Length - defaults to 25 lines; if set to 66 lines, CO/SESSION will support the Genius terminal from Micro Display Systems; <T> Fast Graphics - defaults to NO which means that all graphic screen information is transmitted to the Support computer; when this option is set to YES, alternating lines of graphic screen information are skipped and not sent to the Support computer; the Support user may dynamically control this option by pressing <Ctrl><Alt><T> to toggle Fast Graphics on and off; <U> File Access Directory Restriction - this field is used to define the disk drives and directories which you want to limit the access to by the remote CO/SESSION user when that user is in the CO/SESSION file functions. It does not attempt to restrict access if the remote user is operating DOS on your computer. You define the drives and directories using standard DOS syntax, that is, drive designator followed by a directory; a drive designator must ALWAYS precede the directory; for example, "C:\PUBLIC". Once you define a drive and path, remote access may only be made to the drives and directories, and associated subdirectories, that you specify. Like the DOS "PATH" command, you separate drive/directory specifications by a semi-colon. For example, C:\PUBLIC;C:\UTILITIES;A:;B:;F:\PUBLIC this specification limits access to directories "\PUBLIC" and "\UTILITIES", and their associated subdirectories, on the "C:" drive, all of the "A:" and "B:" drives, and only directory "\PUBLIC" and its subdirectories on the "F:" drive; attempted access to any other drives or directories are not permitted from the remote CO/SESSION File functions menus; <V> Video Mode Synchronize - this field is used in conjunction with the support keyboard command <Ctrl><LeftShift><M>; the field defines the video mode on the APPLICATION computer which CO/SESSION will "synchronize" on, without actually affecting the setting of the video mode; the possible modes are 0 through 7 and match the original IBM CGA and Monochrome video display mode definitions. ANSI.SYS and SIMILAR DEVICE DRIVERS When using CO/SESSION on a system using "ansi.sys", or any similar device driver, be sure to change the CO/SESSION configuration settings to reflect this condition. The configuration setting "Special Console Device Driver", selected by pressing <Q>, should be set to YES if "device=ansi.sys" is specified in your "config.sys" file. REMOTE PRINTING For remote printing to be performed, the application user's PC must be set for remote printing and the support PC user must activate printing or spooling on the support machine. A support user can change the printing status on the application PC using "sprinto". Refer to Section 7 in the User Guide for a complete description of how to set up the APPLICATION and SUPPORT computers for remote printing. MAKING APPLICATION PRINT MODE PERMANENT When setting the application PC for remote printing, you are now prompted as to whether you want the option to be permanent. If you respond with a 'y' for yes, then the selected application print mode is saved on disk. The next time CO/SESSION is loaded the application print mode is set to the saved selected option. It remains permanent until changed. See the previous section above on REMOTE PRINTING/SPOOLING. UNATTENDED REMOTE ACCESS Listed below are the recommended configuration settings on an application machine for unattended remote access. Configuration settings can be changed locally or remotely on an application machine by using "sconfig". <B> Wait Dial-In Mode YES <D> Allow Dial-In On Confirm Timeout YES <N> Reboot Application on Support Hangup YES In conjunction with setting the Wait Dial-In configuration setting to YES, you must also insure that the "DEFAULT" Call ID record has its port parameters set to match the port, baud rate and modem type which you are using. CO/SESSION can be used in conjunction with a power control device from Dynatech called Turn-On for remote, unattended power up and power down of your computer. Dynatech may be reached at 1-408-438-5760. THE DEFAULT CALL ID RECORD Created during the installation of CO/SESSION is a Call ID record named DEFAULT. The port parameters of the DEFAULT Call ID are used when CO/SESSION is loading with the Auto- Answer option enabled, when using the <F1> function in the CO/SESSION Main Menu without defining a "special" Call ID record, and when using the <F7> function in the CO/SESSION Main Menu for the voice first feature when switching to data. QUICK CONNECTIONS TO A PRIMARY SITE Establishing connections with a primary remote system can be made quickly by using the <F1> function in the CO/SESSION Main Menu and setting up a Call ID record as "special" in the configuration settings. Refer to the <L> configuration setting. This feature is especially useful for someone working at home constantly accessing his office PC or a remote PC station constantly calling a central support station for assistance. For additional information see pages 35 and 98 of the CO/SESSION User Guide.